Add Trustabl security scanning to CI - #182
Open
joshua-trustabl wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We came across your repo and we like how you are creating a framework to bridge the gap between human interactions and AI capabilities in video conferencing. We scanned the repo, and noticed agent runtime reliability findings that might be worth reviewing.
[MEDIUM] LangChain tool returns its output directly, bypassing the model
File: examples/client_example.py
What it means: This tool sets return_direct=True, so LangChain returns the tool's raw output straight to the caller and stops the agent loop — the model never sees the result, cannot validate or summarize it, and any output guardrail or post-processing step is skipped.
[MEDIUM] Mutating tool has no idempotency key
File: joinly/server.py
What it means: The tool name signals a side effect (create/send/refund/…), but there's no way to ensure repeated invocations don't lead to unintended duplicate actions if the context isn't perfectly managed.
Recommendations are based on our understanding of agent runtime reliability, some findings may be intentional. Please let us know if this was intentional or if our findings are helpful so we can improve the accuracy of the scanner.
Best,
Trustabl.ai
Open-source AI agent reliability scanner (runs locally, GitHub Action)